Once planning for change is finalized, the Change Coordinator must coordinate with the Release Manager and the respective Delivery Teams to realize the change.

In case the change is small (as agreed in the Service Governance Plan), the Delivery Teams should adopt the Maintenance Change Request process to realize the change. If the change is large, the Delivery Teams should adopt an appropriate software engineering method (waterfall, agile, etc.) along with Unified Project Management (UPM) method, to realize the change.

As a part of realization, the delivery teams should understand the requirements of the assigned change. Functional and technical designs must be prepared/modified and reviewed. The teams should come up with a test strategy to define the levels of testing, test environment, test cases, etc. The code must be developed or modified and reviewed as per the requirements. The teams must then execute testing as detailed in test strategy. Once testing is complete, the success of testing should be verified. Back-out procedures must be tested to ensure minimum impact on service quality in case the change fails. The change must then be released into the desired environment. Appropriate technology configuration management processes must be followed throughout the change realization lifecycle.

The Change Coordinator should monitor the progress to ensure all activities are completed as per schedule. There may be issues or queries encountered by Delivery Teams, which require additional information. In such cases the Change Coordinator must reach out to Change Manager or Change Requester or relevant stake holders to get the required inputs and help the teams resolve the issues and proceed with the change. The Change Coordinator must also ensure that the Change Record is updated with the progress and outcome of the build and test activities.